home *** CD-ROM | disk | FTP | other *** search
- GBLIB1 was written as a companion to Visual Basic.
- There were 2 criteria for including a function or subroutine in the library.
-
- Either: 1) Visual Basic was unable to do it.
- or 2) It saved tedious and/or complicated API declarations.
-
- In category (1) are the SubClassing and Cursor functions.
- In Category (2) are the Resource and Sound functions.
-
- As much effort went into the help file GBLIB1.HLP as the DLL itself.
- This is because a DLL library is only useful if the functions are understood
- in their syntax and use.
-
- Each Subroutine or Function has an explanation of it's use, the original
- Pascal Prototype (so that it can be used with other languages) the Visual
- Basic Declaration, and, where appropriate, an example of how it can be used.
-
- There were two important aims in writing the code:
- 1) All routines should be 'system-resource-friendly', in that they should
- return any resources they consume. (eg DCs, Handles, Objects)
- 2) All routines should be as robust as possible, and capable of detecting
- their own errors.
- Most routines check the parameters passed to them, and will return cleanly
- if they are bad, usually with a Message Box outlining the problem, and any
- resources returned.
- Most functions return Zero for success, and 1 for failure. (except those which
- retrieve a value, of course)
-
- The DLL and associated help file are distributed as FREEWARE, under conditions
- outlined in the help file (See About)
-
- The DLL was written in Borland Turbo Pascal for Windows(tm) V1.5 and the
- help file was written using Microsoft Word for Windows(tm) V6.0
-
- Gordon Bamber 30/08/94
-